Conservation of resources in a mesh network

ABSTRACT

A method including determining, by a first device communicating meshnet data via a meshnet connection with a second device in a mesh network, occurrence of a downgrade triggering event indicating that the first device and the second device are to communicate the meshnet data via a relay connection; transmitting, by the first device to the second device based on determining the occurrence of the downgrade triggering event, a downgrade message; determining, by the first device communicating the meshnet data via the relay connection, occurrence of an upgrade triggering event indicating that the first device and the second device are to communicate the meshnet data via a new meshnet connection; and transmitting, by the first device to the second device based on determining the occurrence of the upgrade triggering event, an upgrade message is disclosed. Various other aspects are contemplated.

CROSS REFERENCE

This application is a continuation of U.S. Non-Provisional patentapplication Ser. No. 17/891,114, filed on Aug. 18, 2022, and titled“Conservation Of Resources In A Mesh Network,” the entire contents ofwhich are incorporated herein by reference.

FIELD OF DISCLOSURE

Aspects of the present disclosure generally relate to communications innetworks, and more particularly to conservation of resources in a meshnetwork.

BACKGROUND

Users may rely on mesh networks (also referred to as “meshnets”) tocommunicate (e.g., transmit and/or receive) data among a plurality ofendpoints (e.g., user devices) via one or more Internet nodes (e.g.,bridges, switches, infrastructure devices, etc.). In an example, a meshnetwork may include a plurality of endpoints communicatively coupled toeach other directly or via the one or more Internet nodes. A meshnetwork in which all endpoints are communicatively coupled to each othermay be referred to as a fully connected network. Data transmitted by afirst endpoint, from among the plurality of endpoints, may be routedover the Internet via the one or more Internet nodes to a secondendpoint from among the plurality of endpoints. Also, data transmittedby the first endpoint may be routed to two or more endpoints from amongthe plurality of endpoints.

In a mesh network, the plurality of endpoints may cooperate with eachother to enable communication of the data among the plurality ofendpoints. In an example, one or more of the endpoints may participatein communication of the data. In this way, the mesh network may avoidrelying on a given endpoint for communication of the data. Some meshnetworks may have the ability to dynamically self-organize andself-configure the plurality of endpoints. This ability may allow suchmesh networks to enable dynamic distribution of workloads, particularlyin the event that one or more endpoints should fail. Further,installation overhead may be reduced.

SUMMARY

In one aspect, the present disclosure contemplates a method includingdetermining, by a first device in communication with a second device viaa meshnet connection in a mesh network, occurrence of a downgradetriggering event indicating that communication between the first userdevice and the second user device is to be downgraded; and transmitting,by the first device to the second device based at least in part ondetermining occurrence of the downgrade triggering event, a downgrademessage indicating that communication between the first user device andthe second user device is to be downgraded.

In another aspect, the present disclosure contemplates a first deviceincluding a memory and a processor configured to: determine, by a firstdevice in communication with a second device via a meshnet connection ina mesh network, occurrence of a downgrade triggering event indicatingthat communication between the first user device and the second userdevice is to be downgraded; and transmit, by the first device to thesecond device based at least in part on determining occurrence of thedowngrade triggering event, a downgrade message indicating thatcommunication between the first user device and the second user deviceis to be downgraded.

In another aspect, the present disclosure contemplates a non-transitorycomputer readable medium storing instructions, which when executed by aprocessor associated with a first device, cause the processor to:determine, by a first device in communication with a second device via ameshnet connection in a mesh network, occurrence of a downgradetriggering event indicating that communication between the first userdevice and the second user device is to be downgraded; and transmit, bythe first device to the second device based at least in part ondetermining occurrence of the downgrade triggering event, a downgrademessage indicating that communication between the first user device andthe second user device is to be downgraded.

It is to be understood that both the foregoing general description andthe following detailed description are exemplary and explanatory innature and are intended to provide an understanding of the presentdisclosure without limiting the scope thereof. In that regard,additional aspects, features, and advantages of the present disclosurewill be apparent to one skilled in the art from the following detaileddescription.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings illustrate aspects of systems, devices,methods, and/or mediums disclosed herein and together with thedescription, serve to explain the principles of the present disclosure.Throughout this description, like elements, in whatever aspectdescribed, refer to common elements wherever referred to and referencedby the same reference number. The characteristics, attributes,functions, interrelations ascribed to a particular element in onelocation apply to those elements when referred to by the same referencenumber in another location unless specifically stated otherwise.

The figures referenced below are drawn for ease of explanation of thebasic teachings of the present disclosure; the extensions of the figureswith respect to number, position, relationship, and dimensions of theparts to form the following aspects may be explained or may be withinthe skill of the art after the following description has been read andunderstood. Further, exact dimensions and dimensional proportions toconform to specific force, weight, strength, and similar requirementswill likewise be within the skill of the art after the followingdescription has been read and understood.

The following is a brief description of each figure used to describe thepresent disclosure, and thus, is being presented for illustrativepurposes only and should not be limitative of the scope of the presentdisclosure.

FIG. 1 is an illustration of an example system associated withconservation of resources in a mesh network, according to variousaspects of the present disclosure.

FIG. 2 is an illustration of an example associated with conservation ofresources in a mesh network, according to various aspects of the presentdisclosure.

FIG. 3 is an illustration of an example flow associated withconservation of resources in a mesh network, according to variousaspects of the present disclosure.

FIG. 4 is an illustration of an example process associated withconservation of resources in a mesh network, according to variousaspects of the present disclosure.

FIG. 5 is an illustration of an example process associated withconservation of resources in a mesh network, according to variousaspects of the present disclosure.

FIG. 6 is an illustration of an example process associated withconservation of resources in a mesh network, according to variousaspects of the present disclosure.

FIG. 7 is an illustration of example devices associated withconservation of resources in a mesh network, according to variousaspects of the present disclosure.

DETAILED DESCRIPTION

For the purposes of promoting an understanding of the principles of thepresent disclosure, reference will now be made to the aspectsillustrated in the drawings, and specific language may be used todescribe the same. It will nevertheless be understood that no limitationof the scope of the disclosure is intended. Any alterations and furthermodifications to the described devices, instruments, methods, and anyfurther application of the principles of the present disclosure arefully contemplated as would normally occur to one skilled in the art towhich the disclosure relates. In particular, it is fully contemplatedthat the features, components, and/or steps described with respect toone aspect may be combined with the features, components, and/or stepsdescribed with respect to other aspects of the present disclosure. Forthe sake of brevity, however, the numerous iterations of thesecombinations may not be described separately. For simplicity, in someinstances the same reference numbers are used throughout the drawings torefer to the same or like parts.

FIG. 1 is an illustration of an example 100 associated with conservationof resources in a mesh network, according to various aspects of thepresent disclosure. Example 100 shows an architectural depiction ofincluded components. In some aspects, the components may include one ormore user devices 102 capable of communicating with a mesh networkservice provider (MSP) control infrastructure 104 for purposes ofobtaining mesh network services. In some aspects, the one or more userdevices 102 may communicate with the MSP control infrastructure 104 overa network 118. The MSP control infrastructure 104 may be controlled by amesh network service provider and may include an application programminginterface (API) 106, a user database 108, processing unit 110, and ameshnet database 112. In some aspects, a user device 102 may utilize aprocessing unit 116 and/or a client application 114, which is providedby the MSP control infrastructure 104, to communicate with the API 106.The API 106 may be capable of communicating with the user database 108and with the processing unit 110. Additionally, the processing unit 110may be capable of communicating with the meshnet database 112, which maybe capable of storing data associated with providing mesh networkservices.

The user device 102 may be a physical computing device capable ofhosting the client application 114 and of connecting to the network 118.The user device 102 may be, for example, a laptop, a mobile phone, atablet computer, a desktop computer, a smart device, a router, or thelike. In some aspects, the user device 102 may include, for example,Internet-of-Things (IoT) devices such as MSP smart home appliances,smart home security systems, autonomous vehicles, smart health monitors,smart factory equipment, wireless inventory trackers, biometric cybersecurity scanners, or the like. The network 118 may be any digitaltelecommunication network that permits several nodes to share and accessresources. In some aspects, the network 118 may include one or morenetworks such as, for example, a local-area network (LAN), a wide-areanetwork (WAN), a campus-area network (CAN), a metropolitan-area network(MAN), a home-area network (HAN), Internet, Intranet, Extranet, andInternetwork.

The MSP control infrastructure 104 may include a combination of hardwareand software components that enable provision of mesh network servicesto the user device 102. The MSP control infrastructure 104 may interfacewith (the client application on) the user device 102 via the API 106,which may include one or more endpoints to a defined request-responsemessage system. In some aspects, the API 106 may be configured toreceive, via the network 118, a connection request from the user device102 to establish a connection with the MSP control infrastructure 104for purposes of obtaining the mesh network services. The connectionrequest may include an authentication request to authenticate the userdevice 102. The API 106 may receive the authentication request and arequest for the mesh network services in a single connection request. Insome aspects, the API 106 may receive the authentication request and therequest for the mesh network services in separate connection requests.

The API 106 may further be configured to handle the connection requestby mediating the authentication request. For instance, the API 106 mayreceive from the user device 102 credentials including, for example, aunique combination of a user ID and password for purposes ofauthenticating the user device 102. In another example, the credentialsmay include a unique validation code known to an authentic user. The API106 may provide the received credentials to the user database 108 forverification.

The user database 108 may include a structured repository of validcredentials belonging to authentic users. In one example, the structuredrepository may include one or more tables containing valid uniquecombinations of user IDs and passwords belonging to authentic users. Inanother example, the structured repository may include one or moretables containing valid unique validation codes associated withauthentic users. The mesh network service provider may add or deletesuch valid unique combinations of user IDs and passwords from thestructured repository at any time. Based at least in part on receivingthe credentials from the API 106, the user database 108 and a processor(e.g., the processing unit 110 or another local or remote processor) mayverify the received credentials by matching the received credentialswith the valid credentials stored in the structured repository. In someaspects, the user database 108 and the processor may authenticate theuser device 102 when the received credentials match at least one of thevalid credentials. In this case, the mesh network service provider mayprovide mesh network services to the user device 102. When the receivedcredentials fail to match at least one of the valid credentials, theuser database 108 and the processor may fail to authenticate the userdevice 102. In this case, the mesh network service provider may declineto provide mesh network services to the user device 102.

When the user device 102 is authenticated, the user device 102 mayinitiate a connection and may transmit to the API 106 a request for themesh network services. The processing unit 110 included in the MSPcontrol infrastructure 104 may be configured to determine a mesh networkassociated with the user device 102 and/or to identify one or more userdevices to be included within the determined mesh network. Theprocessing unit 110 may utilize the API 106 to transmit informationassociated with the mesh network and/or the identified one or more userdevices to the user device 102. The user device 102 may transmit aninitiation request to establish secure connections (e.g., encryptedtunnels) with the one or more user devices. In some aspects, the one ormore user devices with which the user device 102 establishes the secureconnections may also host respective client applications forcommunicating with the MSP control infrastructure 104 and/or with theuser device 102. In some aspects, the processing unit 110 may be alogical unit including a logical component configured to perform complexoperations associated with computing, for example, numerical weightsrelated to various factors associated with providing the meshnetservices.

One or more components (e.g., API 106, user database 108, processingunit 110, and/or meshnet database 112, processing unit 116) included inthe MSP control infrastructure 104 and/or included in the user device102 may further be associated with a controller/processor, a memory, acommunication interface, or a combination thereof (e.g., FIG. 7 ). Forinstance, the one or more components of the set of components mayinclude or may be included in a controller/processor, a memory, or acombination thereof. In some aspects, the one or more of the componentsincluded in the MSP control infrastructure 104 may be separate anddistinct from each other. Alternatively, in some aspects, the one ormore of the components included in the MSP control infrastructure 104may be combined with one or more of the other components. In someaspects, the one or more of the components included in the MSP controlinfrastructure 104 and/or the user device 102 may be local with respectto each other. Alternatively, in some aspects, one or more of thecomponents included in the MSP control infrastructure 104 and/or theuser device 102 may be located remotely with respect to one or more ofother components included in the MSP control infrastructure 104 and/orthe user device 102. Additionally, or alternatively, one or morecomponents of the components included in the MSP control infrastructure104 and/or the user device 102 may be implemented at least in part assoftware stored in a memory. For example, a component (or a portion of acomponent) may be implemented as instructions or code stored in anon-transitory computer-readable medium and executable by a controlleror a processor to perform the functions or operations of the component.Additionally, or alternatively, a set of (one or more) components shownin FIG. 1 may be configured to perform one or more functions describedas being performed by another set of components shown in FIG. 1 .

As indicated above, FIG. 1 is provided as an example. Other examples maydiffer from what is described with regard to FIG. 1 .

Endpoints (e.g., user devices) may rely on a mesh network to communicate(e.g., transmit and/or receive) meshnet data among the endpoints. Inexample 200 shown in FIG. 2 , the endpoints may include a first userdevice, a second user device, a third user device, and/or a fourth userdevice. The meshnet data may be communicated using wired communicationsand/or wireless communications over a network such as, for example, theInternet. The meshnet data may include any information including digitalinformation such as, for example, documents including data, voice data,image data, signal data, and/or video data. Further, the internal meshnetwork may be a secure mesh network that may enable the endpoints tocommunicate the meshnet data in encrypted form via meshnet connections(shown as double-ended arrows in FIG. 2 ).

Each endpoint may be associated with a respective local area network(LAN) and may utilize a respective local port to communicate the meshnetdata. In turn, the respective LAN may be associated with a respectivenetwork address translation (NAT) device for conducting NAT procedures,including mapping the respective local port with a respective publicport (e.g., UDP port, TCP port, etc.). The NAT device may route themeshnet data transmitted by the respective local port to the respectivepublic port and then to another endpoint in the mesh network. Similarly,the NAT device may receive meshnet data transmitted by another endpointat the respective public port and may route the received meshnet data tothe respective local port.

With respect to the first user device, while conducting the NATprocedures, a first NAT device may reallocate a first public port(and/or a first public IP address) for tasks other than routing themeshnet data and may allocate a second public port (and/or a secondpublic IP address) for routing the meshnet data. In an example, suchreallocation may be due to lack of communication in the mesh network bythe first user device for a threshold amount of time (e.g., 60 seconds,90 seconds, 120 seconds, etc.), or for a need that the first public portsupports a task other than routing the meshnet data, or the like.Because the first user device and other endpoints in the mesh networkare unaware of the reallocation of the first public port, the endpointsmay continue to communicate the meshnet data to the first public port.The NAT device may drop and/or discard such meshnet data communicated tothe first public port. As a result, the first user device may fail toreceive the communicated meshnet data.

To avoid reallocation of the first public port such that communicatedmeshnet data is not dropped and/or discarded, the first user device mayperiodically (e.g., every 25 seconds) transmit keep-alive signals evenwhen the first user device is not actively communicating meshnet data.The keep-alive signals may indicate to the first NAT device that thefirst user device is actively communicating with the other endpoints inthe mesh network. The first user device may transmit respectivekeep-alive signals to each of the other endpoints in the mesh network.

Such periodic transmission of respective keep-alive signals to each ofthe other endpoints may inefficiently consume user device resources(e.g., processing resources, memory resources, power consumptionresources, battery life, or the like) and network resources(computational resources, network bandwidth, management resources,processing resources, memory resources, or the like) that can otherwisebe utilized to perform suitable tasks associated with the mesh network.Further, network resources may be inefficiently expended to maintain themeshnet connections even when the first user device is not activelycommunicating meshnet data. The above discussion with respect to thefirst user device may also apply to the one or more endpoints in themesh network.

Various aspects of systems and techniques discussed in the presentdisclosure enable conservation of resources in a mesh network. In someaspects, an MSP control infrastructure may provide the mesh network toenable endpoints to securely communicate meshnet data. Further, the MSPcontrol infrastructure may provide the endpoints with respective clientapplications to communicate with the MSP control infrastructure, tocommunicate with each other for setting up respective meshnetconnections to be utilized for communicating meshnet data in the meshnetwork, and/or to communicate the meshnet data with each other over therespective meshnet connections. The MSP control infrastructure and therespective client applications may also enable conservation of resourcesin a mesh network. In some aspects, a first client application mayperform conservation of resources based at least in part on monitoringoccurrence of triggering events associated with communicating themeshnet data. Based at least in part on determining occurrence of atriggering event, the first client application may downgrade thecommunication to utilize a relay connection (instead of a meshnetconnection) to communicate with another user device. In some aspects,determining occurrence of a triggering event may include determiningthat an amount of meshnet data to be communicated by the first clientapplication is less than a threshold data amount, or that the firstclient application has not communicated meshnet data for a giveninterval of time, etc. During the downgraded communication, instead oftransmitting respective keep-alive signals to each of the otherendpoints in the mesh network, the first client application mayperiodically transmit keep-alive signals to the MSP controlinfrastructure for maintenance of the relay connection. In other words,the first client application may avoid transmitting several keep-alivesignals. In this way, instances of inefficient transmissions of severalkeep-alive signals by the first user device may be mitigated. Further,because other client applications may also transmit the keep-alivesignals to the MSP control infrastructure, the first client applicationmay avoid expending user device resources to receive and/or processkeep-alive signals from the other endpoints. As a result, the MSPcontrol infrastructure and the respective client applications may enableefficient utilization of user device resources (e.g., processingresources, memory resources, power consumption resources, battery life,or the like) and network resources (computational resources, networkbandwidth, management resources, processing resources, memory resources,or the like) for performing suitable tasks associated with the meshnetwork.

In some aspects, a processor (e.g., processing unit 116, processor 720)associated with a user device may determine, while in communication witha second device via a meshnet connection in a mesh network, occurrenceof a downgrade triggering event indicating that communication betweenthe first user device and the second user device is to be downgraded;and transmit, to the second device based at least in part on determiningoccurrence of the downgrade triggering event, a downgrade messageindicating that communication between the first user device and thesecond user device is to be downgraded.

As indicated above, FIG. 2 is provided as an example. Other examples maydiffer from what is described with regard to FIG. 2 .

FIG. 3 is an illustration of an example flow 300 associated withconservation of resources in a mesh network, according to variousaspects of the present disclosure. The example flow 300 may include afirst user device (e.g., first endpoint), MSP control infrastructure104, and a second user device (e.g., second endpoint) in communicationwith each other. The first user device and the second user device may besimilar to a user device 102 discussed above with respect to FIG. 1 . Insome aspects, the first user device and the second user device may beassociated with a single account registered with the MSP controlinfrastructure 104. In some aspects, the first user device and thesecond user device may be associated with different accounts registeredwith the MSP control infrastructure 104. In some aspects, the first userdevice and the second user device may be located locally (e.g., in thesame room, in the same building, etc.). In some aspects, the first userdevice and the second user device may be located remotely (e.g., indifferent buildings, in different cities, in different states, indifferent countries, etc.) with respect to each other.

The first user device may install a first client application (e.g.,client application 104) and the second user device may install a secondclient application (e.g., client application 104), the first clientapplication and the second client application being associated with(e.g., provided by) the MSP control infrastructure 104. The first userdevice and the second user device may use the respective clientapplications to communicate with an application programming interface(API) and/or a processor (e.g., processing unit 110, processor 720)associated with the MSP control infrastructure 104. In some aspects, thefirst user device, the MSP control infrastructure 104, and the seconduser device may communicate with each other over a network (e.g.,network 118). As discussed elsewhere herein, the MSP controlinfrastructure 104 may enable the first user device and/or the seconduser device to obtain the mesh network services.

In some aspects, the client applications may enable the user devices toreceive information to be processed by the client applications and/or bythe MSP control infrastructure 104. Each of the client applications mayinclude respective graphical user interfaces to receive the informationvia local input interfaces (e.g., touch screen, keyboard, mouse,pointer, etc.) associated with the user devices. The information may bereceived via text input or via a selection from among a plurality ofoptions (e.g., pull down menu, etc.). In some aspects, the first clientapplication and/or the second client application may activate and/orenable, at a time associated with the registration (e.g., after theregistration), the graphical interface for receiving the information.For instance, the first client application (or the second clientapplication) may cause a screen (e.g., local screen) associated with thefirst user device (or the second user device) to display, for example, apop-up message to request entry of the information. Further, the clientapplications may enable transmission of at least a portion of theinformation to the MSP control infrastructure 104. In some aspects, thefirst client application may utilize a first processing unit (e.g.,processing unit 116, processor 720) associated with the first userdevice to perform processes/operations associated with obtaining themesh network services and the second application may utilize a secondprocessing unit (e.g., processing unit 116, processor 720) associatedwith the second user device to perform processes/operations associatedwith obtaining the mesh network services.

Although only two user devices (e.g., endpoints) are shown in FIG. 3 ,the present disclosure contemplates the mesh network to include anynumber of user devices that perform the processes discussed herein in asimilar and/or analogous manner. For instance, the mesh network mayinclude a third user device and a fourth user device, as discussed abovewith respect to FIG. 2 , that perform the processes discussed herein ina similar and/or analogous manner. Further, user devices may leave orjoin the mesh network in an ad-hoc manner.

As shown by reference numeral 305, the first user device may register anaccount with the MSP control infrastructure 104. In some aspects, duringthe registration, the first user device may provide registrationinformation such as, for example, identity of an owner of the first userdevice, a phone number associated with the first user device, an emailaddress associated with the first user device, or the like. In someaspects, the first user device may set up an access system includinglogin information (e.g., access information) such as, for example,username, password, or the like to subsequently gain access to theregistered account. In some aspects, the first user device may share thelogin information with other user devices (e.g., second user device)associated with the first user device to enable the other user devicesto utilize the login information to gain access to the MSP controlinfrastructure 104 via the registered account. In some aspects, a givenuser device may be associated with the first user device because thegiven user device may be available to a user/owner of the first userdevice. In some aspects, when the second user device is not associatedwith the registered account associated with the first user device, thesecond user device may register a different account with the MSP controlinfrastructure 104.

In some aspects, the first user device and the second user device mayutilize the login information to access the registered account/accountsto communicate with the MSP control infrastructure 104. As shown byreference numeral 310, based at least in part on the first user deviceand the second user device accessing the registered account/accounts tocommunicate with the MSP control infrastructure 104, the MSP controlinfrastructure 104 may transmit, and the first client application andthe second client application may receive, MSP access information. Insome aspects, the MSP access information may include UDP accessinformation. The UDP access information may include informationregarding an infrastructure UDP IP address and an infrastructure UDPport associated with the MSP control infrastructure 104. The MSP controlinfrastructure 104 may utilize the infrastructure UDP IP address and theinfrastructure UDP port to communicate utilizing the UDP. In someaspects, the first user device and the second user device may utilizethe infrastructure UDP IP address and the infrastructure UDP port tocommunicate with the MSP control infrastructure 104 regarding the meshnetwork. Further, the first client application and the second clientapplication may obtain from, for example, a domain name services (DNS)server, transmission control protocol (TCP) access informationassociated with the MSP control infrastructure 104. Such TCP accessinformation may include information regarding an infrastructure TCP IPaddress and an infrastructure TCP port associated with the MSP controlinfrastructure 104. The MSP control infrastructure 104 may utilize theinfrastructure TCP IP address and the infrastructure TCP port tocommunicate utilizing the TCP.

As shown by reference numeral 315, the first client application and thesecond client application may determine information based at least inpart on the registration of the account/accounts with the MSP ControlInfrastructure 104. In an example, the first client application maydetermine an asymmetric first assigned key pair associated with thefirst user device. The first assigned key pair may be unique to thefirst user device and may include a first assigned public key and afirst assigned private key. In this way, the first assigned public keyand the first assigned private key may be device-specific and maybeassociated with the registered account. In some aspects, the firstassigned public key and the first assigned private key may be associatedwith each other via, for example, a mathematical function. As a result,data encrypted using the first assigned public key may be decrypted byutilizing the first assigned private key.

Similarly, the second client application may determine an asymmetricsecond assigned key pair associated with the second user device. Thesecond assigned key pair may be unique to the second user device and mayinclude a second assigned public key and a second assigned private key.In this way, the second assigned public key and the second assignedprivate key may be device-specific and maybe associated with theregistered account. In some aspects, the second assigned public key andthe second assigned private key may be associated with each other via,for example, a mathematical function. As a result, data encrypted usingthe second assigned public key may be decrypted by utilizing the secondassigned private key.

As shown by reference numeral 320, the client applications may transmit,and the MSP control infrastructure 104 may receive, at least a portionof the information determined by the client applications. For instance,the first client application may transmit, for example, the firstassigned public key to the MSP control infrastructure 104 and the secondclient application may transmit, for example, the second assigned publickey to the MSP control infrastructure 104. The MSP controlinfrastructure 104 may store and correlate the received information inassociation with the registered account and/or with the respective userdevices. In an example, the MSP control infrastructure 104 may store andcorrelate the first assigned public key in association with theregistered account and the first user device, and may store andcorrelate the second assigned public key in association with theregistered account and the second user device. In some aspects, thefirst client application and the second client application may utilizethe infrastructure TCP IP address and the infrastructure TCP port totransmit the first assigned public key and the second assigned publickey to the MSP control infrastructure 104 via the TCP.

Further, as shown by reference numeral 325, the MSP controlinfrastructure 104 may determine that the first user device and thesecond user device are to be included in the same mesh network. In someaspects, when the first user device and the second user device areassociated with the same registered account, the MSP controlinfrastructure 104 may make such a determination regarding the securemesh network based at least in part on determining that the first userdevice and the second user device are communicating with the MSP controlinfrastructure 104 by utilizing the login information associated withthe same registered account. In some aspects, when the first user deviceand the second user device are associated with different registeredaccounts, the MSP control infrastructure 104 may make such adetermination regarding the secure mesh network based at least in parton the first user device (and/or the second user device) providinginformation indicating that the first user device and the second userdevice are to be included in the same mesh network. Such information mayinclude, for example, identification information (e.g., type of device,user name, email address, etc.) associated with the second user device(or the first user device), the second IP address (or the first IPaddress), or the like.

Based at least in part on determining that the first user device and thesecond user device are to be included in the same mesh network, as shownby reference numeral 330, the MSP control infrastructure 104 maydetermine meshnet IP addresses for the first user device and for thesecond user device. In an example, the MSP control infrastructure 104may determine a first meshnet IP address associated with the first userdevice and a second meshnet IP address associated with the second userdevice. The first client application and/or another applicationinstalled on the first user device and/or the operating systemassociated with the first user device may utilize the first meshnet IPaddress and/or the first local meshnet port to communicate data with theendpoints over meshnet connections in the mesh network and the seconduser device may utilize the second meshnet IP address and/or the secondlocal meshnet port to communicate data with the endpoints over themeshnet connections in the mesh network. In an example, with respect tocommunication between the first user device and the second user device,the first user device may determine a first meshnet IP packet indicatingthe first meshnet IP address as a source address, the first localmeshnet port as a source port, the second meshnet IP address as adestination address, and the second local meshnet port as a destinationport. The first user device may encrypt and encapsulate the firstmeshnet IP packet within a payload of a transmitted UDP IP packet. Thesecond user device may receive the UDP IP packet, may decrypt the firstmeshnet IP packet, and may route the first meshnet IP packet to thesecond local meshnet port. Similarly, the second user device maydetermine a second meshnet IP packet indicating the second meshnet IPaddress as a source address, the second local meshnet port as a sourceport, the first meshnet IP address as a destination address, and thefirst local meshnet port as a destination port. The second user devicemay encrypt and encapsulate the second meshnet IP packet within apayload of a transmitted UDP IP packet. The first user device mayreceive the UDP IP packet, may decrypt the first meshnet IP packet, andmay route the second meshnet IP packet to the first local meshnet port.The MSP control infrastructure 104 may determine the first meshnet IPaddress and the second meshnet IP address from, for example, a pool ofreserved IP addresses included in a subnet associated with an internalnetwork of the ISP.

As shown by reference numeral 335, the first user device and the seconduser device may transmit, and the MSP control infrastructure 104 mayreceive, respective binding requests. In some aspects, the first userdevice may transmit the first binding request to the MSP controlinfrastructure 104 using the UDP by utilizing the UDP access informationreceived from the MSP control infrastructure 104 (e.g., block 320). Inthis case, the first user device may transmit a first binding request tothe MSP control infrastructure 104 to request the MSP controlinfrastructure 104 to determine a first public UDP IP address (e.g.,communication address) and/or a first public UDP port (e.g.,communication port) associated with the first user device. As discussedbelow in further detail, the first public UDP IP address and/or thefirst public UDP port are to be utilized by the second user device tocommunicate with the first user device in the mesh network. Similarly,the second user device may transmit the second binding request to theMSP control infrastructure 104 using the UDP by utilizing the UDP accessinformation received from the MSP control infrastructure 104 (e.g.,block 320). In this case, the second user device may transmit a secondbinding request to the MSP control infrastructure 104 to request the MSPcontrol infrastructure 104 to determine a second public UDP IP address(e.g., communication address) and/or a second public UDP port (e.g.,communication port) associated with the second user device. As discussedbelow in further detail, the second UDP IP address and/or the second UDPport are to be utilized by the first user device to communicate with thesecond user device in the mesh network.

In some aspects, the first public UDP IP address and/or the first publicUDP port may be determined by a first NAT device (e.g., a router)responsible for managing operation of the first user device in a firstlocal network. In an example, the first NAT device may translate a firstlocal UDP IP address and/or a first local UDP port associated with thefirst user device to the first public UDP IP address and/or the firstpublic UDP port that the first user device utilizes to communicate(e.g., transmit and/or receive) over the Internet using the UDP.Similarly, the second public UDP IP address and/or the second public UDPport may be determined by a second NAT device responsible for managingoperation of the second user device in a second local network. In anexample, the second NAT device may translate a second local UDP IPaddress and/or a second local UDP port associated with the second userdevice to the second public UDP IP address and/or the second public UDPport that the second user device utilized to communicate (e.g., transmitand/or receive) over the Internet using the UDP.

Based at least in part on receiving the respective binding requests, asshown by reference numeral 340, the MSP control infrastructure 104 maydetermine public UDP IP addresses and/or public UDP ports associatedwith the first user device and the second user device. In an example,based at least in part on receiving the first binding request, the MSPcontrol infrastructure 104 may determine the first public UDP IP addressand/or the first public UDP port associated with the first user device.In some aspects, the MSP control infrastructure 104 may determine thefirst public UDP IP address and/or the first public UDP port based atleast in part on analyzing the UDP communication (e.g., UDP IP packet)including the first binding request received from the first user device.The UDP communication may include, for example, a header that indicatesthe first public UDP IP address as a source UDP IP address and/or thefirst public UDP port as a source UDP port associated with the firstuser device. Further, the MSP control infrastructure 104 may store andcorrelate the first public UDP IP address and/or the first UDP port inassociation with the first user device in, for example, the meshnetdatabase 112. Similarly, based at least in part on receiving the secondbinding request, the MSP control infrastructure 104 may determine thesecond public UDP IP address and/or the second public UDP portassociated with the second user device. In some aspects, the MSP controlinfrastructure 104 may determine the second public UDP IP address and/orthe second public UDP port based at least in part on analyzing the UDPcommunication (e.g., UDP IP packet) including the second binding requestreceived from the second user device. The UDP communication may include,for example, a header that indicates the second public UDP IP address asa source UDP IP address and/or the second public UDP port as a sourceUDP port associated with the second user device. Further, the MSPcontrol infrastructure 104 may store and correlate the second public UDPIP address and/or the second public UDP port in association with thesecond user device in, for example, the meshnet database 112.

Based at least in part on determining the public UDP IP addresses and/orthe public UDP ports, as shown by reference numeral 345, the MSP controlinfrastructure 104 may transmit, and the first client application andthe second client application may receive, communication information. Inan example, the MSP control infrastructure 104 may transmit, and thefirst client application may receive, first communication informationincluding the first meshnet IP address associated with the first userdevice, the second meshnet IP address associated with the second userdevice, the second public UDP IP address and/or the second public UDPport associated with the second user device, and the second public keyassociated with the second user device. Similarly, the MSP controlinfrastructure 104 may transmit, and the second client application mayreceive, second communication information including the first public UDPIP address and/or the first public UDP port associated with the firstuser device, the first public key associated with the first user device,the first meshnet IP address associated with the first user device, andthe second meshnet IP address associated with the second user device. Asdiscussed below in further detail, the above transmission ofcommunication information may enable the first user device and thesecond user device to communicate securely and privately in the meshnetwork.

As shown by reference numeral 350, the first client application and thesecond client application may communicate with each other directly toset up a meshnet connection (e.g., an encrypted tunnel) forcommunicating encrypted data in the mesh network. To set up the meshnetconnection, the first client application may utilize the second assignedpublic key and/or the second public IP address (e.g., second UDP IPaddress) to securely (e.g., in encrypted form) communicate with thesecond client application, and the second client application may utilizethe first assigned public key and/or the first public IP address (e.g.,first UDP IP address) to securely communicate with the first clientapplication. In some aspects, the first client application and thesecond client application may communicate to securely/privatelynegotiate parameters (e.g., a symmetric encryption/decryption key)associated with the meshnet connection. In some aspects, the parametersmay be randomly generated to provide optimized security to thecommunications. In an example, the first client application and thesecond client application may privately negotiate a randomly generatedsymmetric key that is to be utilized by the first client application andthe second client application for encrypting and decrypting datacommunicated via the meshnet connection. The randomly generatedsymmetric key may be determined based at least in part on anycombination of the first public key, the second public key, and/orrandomly generated numbers. Additionally, the first client applicationand the second client application may utilize a secure protocol (e.g.,Wireguard, IP sec, etc.) to communicate the data via the meshnetconnection.

Additionally, or alternatively, the first client application and thesecond client application may communicate with each other indirectlyvia, for example, a relay device (e.g., a relay server) to set up themeshnet connection. In an example, the first client application mayprovide the first assigned public key to a relay server, which may storean association of the first assigned public key with the first clientapplication. In some aspects, the association may include an associationbetween the first assigned public key and a first communicationconnection between the relay server and the first client application.Similarly, the second client application may provide the second assignedpublic key to the relay server, which may store an association of thesecond assigned public key with the second client application. In someaspects, the association may include an association between the secondassigned public key and a second communication connection between therelay server and the first client application. The relay server may relyon the stored associations of public keys and client applications todetermine a destination of a received message. In some aspects, therelay server may include a network of relay servers that enable thefirst client application and the second client application tocommunicate with each other. In this case, the first client applicationand the second client application may provide the respective assignedpublic keys to different relay servers included within the network ofrelay servers.

In some aspects, the first client application may transmit, to the relayserver, a first message that is to be delivered to the second clientapplication. Along with the first message, the first client applicationmay transmit the second assigned public key. Further, the first clientapplication may encrypt the first message utilizing the second assignedpublic key. In some aspects, the first client application may encryptthe first message based at least in part on utilizing the negotiatedrandomly generated symmetric key. Based at least in part on receivingthe encrypted first message and the second assigned public key, therelay server may determine from stored associations that the secondassigned public key is associated with the second client application. Asa result, the relay server may determine that the first message is to berelayed (e.g., transmitted) to the second client application. Similarly,the second client application may transmit, to the relay server, asecond message that is to be delivered to the first client application.Along with the second message, the second client application maytransmit the first assigned public key. Further, the second clientapplication may encrypt the second message utilizing the first assignedpublic key. In some aspects, the second client application may encryptthe second message based at least in part on utilizing the negotiatedrandomly generated symmetric key. Based at least in part on receivingthe encrypted second message and the first assigned public key, therelay server may determine from stored associations that the firstassigned public key is associated with the first client application. Asa result, the relay server may determine that the second message is tobe relayed (e.g., transmitted) to the first client application. In thisway, the relay server may enable the first client application and thesecond client application to communicate with each other to set up themeshnet connection.

Based at least in part on establishing (e.g., setting up) the meshnetconnection, the first client application and the second clientapplication may begin communicating encrypted data via the meshnetconnection based at least in part on utilizing the negotiated parametersand the secure protocol. In a similar and/or analogous manner, the firstclient application may set up meshnet connections with a third clientapplication installed in the third user device and with a fourth clientapplication associated with the fourth user device. Also, in a similarand/or analogous manner, the second client application may set upmeshnet connections with the first client application, the third clientapplication, and the fourth client application. Further, in a similarand/or analogous manner, the third client application may set up meshnetconnections with the first client application, the second clientapplication, and the fourth client application. Finally, in a similarand/or analogous manner, the fourth client application may set upmeshnet connections with the first client application, the second clientapplication, and the third client application. Additional clientapplications that enter the mesh network may also set up meshnetconnections with the other client applications included in the meshnetwork in a similar and/or analogous manner.

As shown by reference numeral 355, the first user device and/or thesecond user device may perform conservation of resources in the meshnetwork. In some aspects, performing conservation of resources mayinclude downgrading communications such that meshnet data iscommunicated via a relay connection instead of the meshnet connection.Further, performing conservation of resources may include upgradingcommunications such that meshnet data is communicated via the meshnetconnection instead of the relay connection. In some aspects, the relayconnection may enable communication of meshnet data via a relay server,as discussed elsewhere herein.

With respect to the first user device, based at least in part on settingup the meshnet connection, the first user device (e.g., first clientapplication) may perform conservation of resources by monitoring anoccurrence of a downgrade triggering event associated with thedowngrading the communications. The first user device may determine thatthe downgrade triggering event has occurred based at least in part on arate of communication of meshnet data via the meshnet connection.

In one example, the downgrade triggering event may be a throughput-basedtriggering event associated with an amount of meshnet data communicatedper unit time. For instance, the first user device may measure an amountof meshnet data communicated per unit time (e.g., 60 seconds, 90seconds, 120 seconds, etc.), and compare the measured amount of meshnetdata with a predetermined downgrade data threshold (e.g., 250 bytes persecond, 500 bytes per second, 1000 bytes per second, etc.). In someaspects, the first user device may calculate an average amount ofmeshnet data for comparison with the downgrade data threshold. When themeasured amount of meshnet data satisfies the downgrade data threshold(e.g., the measured amount of meshnet data is equal to or greater thanthe predetermined data threshold), the first user device may determinethat the first user device is actively communicating meshnet data with,for example, the second user device. In this case, the first user devicemay determine that the first user device is not to downgrade thecommunications. Alternatively, when the measured amount of meshnet datafails to satisfy the downgrade data threshold (e.g., the measured amountof meshnet data is less than the predetermined data threshold), thefirst user device may determine that the first user device iscommunicating meshnet data such that communications may be downgraded toconserve resources. In this case, the first user device may determinethat the downgrade triggering event has occurred.

In another example, the downgrade triggering event may be a time-basedtriggering event associated with (a lack of) communication of meshnetdata within a given interval of time. For instance, the first userdevice may monitor meshnet data communications within a given intervalof time (e.g., 60 seconds, 90 seconds, 120 seconds, etc.). In someaspects, the first user device may measure the given interval of time byutilizing a timer, which may start based at least in part on acommunication (e.g. transmission and/or reception) of meshnet data. Whenthe first user device determines that the first user device hascommunicated meshnet data within the given interval of time, the firstuser device may determine that the first user device is activelycommunicating meshnet data. In this case, the first user device maydetermine that the first user device is not to downgrade thecommunications. Alternatively, when the first user device determinesthat the first user device has communicated substantially no meshnetdata within the given interval of time, the first user device maydetermine that communications may be downgraded to conserve resources.In this case, the first user device may determine that the downgradetriggering event has occurred.

In yet another example, the downgrade triggering event may be atime-based triggering event associated with the availability of meshnetdata for communication within a given interval of time. For instance,the first user device may monitor an amount of meshnet data that isavailable for communication within the given interval of time (e.g., 60seconds, 90 seconds, 120 seconds, etc.). When the first user devicedetermines that meshnet data is available for transmission within thegiven interval of time (e.g., meshnet data is to be communicated withinthe given interval of time), the first user device may determine thatthe first user device is actively communicating meshnet data. In thiscase, the first user device may determine that the first user device isnot to downgrade the communications. Alternatively, when the first userdevice determines that substantially no meshnet data is available fortransmission within the given interval of time (e.g., substantially nomeshnet data is to be communicated within the given interval of time),the first user device may determine that communications may bedowngraded to conserve resources. In this case, the first user devicemay determine that the downgrade triggering event has occurred.

Based at least in part on determining that the downgrade triggeringevent has occurred, the first user device may transmit a downgrademessage to the second user device. In some aspects, the downgrademessage may indicate to the second user device that meshnet datacommunication between the first user device and the second user deviceis to be downgraded such that the meshnet data is to be communicated viathe relay connection. In some aspects, the downgrade message may includea meshnet data packet with an empty (e.g., blank) payload. Receiving thedowngrade message during meshnet data communication via the meshnetconnection and/or the relay server may indicate to the second userdevice that the meshnet data communication between the first user deviceand the second user device is to be downgraded. As a result, the firstuser device and the second user device may downgrade the communicationssuch that meshnet data between the first user device and the second userdevice is communicated via the relay connection. In this case, the firstuser device and/or the second user device may disconnect the meshnetconnection.

In some aspects, the downgrade message may be transmitted to the seconduser device via the relay server, as discussed elsewhere herein. Forinstance, the first user device may encrypt the downgrade messageutilizing the second public key associated with the second user deviceand/or the symmetric key negotiated between the first user device andthe second user device. The first user device may transmit the encrypteddowngrade message along with the second public key to the relay serverto enable the relay server to relay (e.g., transmit) the encrypteddowngrade message to the second user device. In some aspects, receivinga communication (e.g., downgrade message) via the relay server duringmeshnet data communication via the meshnet connection may indicate tothe second user device that the meshnet data communication between thefirst user device and the second user device is to be downgraded. As aresult, the first user device and the second user device may downgradethe communications such that meshnet data between the first user deviceand the second user device is communicated via the relay connection. Inthis case, the first user device and/or the second user device maydisconnect the meshnet connection. In some aspects, disconnecting themeshnet connection may include discarding the previously negotiatedparameters (e.g., symmetric key, protocol, etc.) during establishment ofthe meshnet connection.

Based at least in part on downgrading the communications, the first userdevice may monitor an occurrence of an upgrade triggering eventassociated with the upgrading the communications such that meshnet datais communicated via the meshnet connection instead of the relayconnection. The first user device may determine that the upgradetriggering event has occurred based at least in part on a rate ofcommunication of meshnet data via the relay connection.

In one example, the upgrade triggering event may be a throughput-basedtriggering event associated with an amount of meshnet data communicatedper unit time. For instance, the first user device may measure an amountof meshnet data communicated via the relay connection per unit time(e.g., 60 seconds, 90 seconds, 120 seconds, etc.), and compare themeasured amount of meshnet data with a predetermined upgrade datathreshold (e.g., 250 bytes per second, 500 bytes per second, 1000 bytesper second, etc.). In some aspects, the first user device may calculatean average amount of meshnet data for comparison with the upgrade datathreshold. when the measured amount of meshnet data fails to satisfy theupgrade data threshold (e.g., the measured amount of meshnet data isless than the upgrade data threshold), the first user device maydetermine that the first user device is not to upgrade thecommunications to continue to conserve resources. Alternatively, whenthe measured amount of meshnet data satisfies the upgrade data threshold(e.g., the measured amount of meshnet data is equal to or greater thanthe upgrade data threshold), the first user device may determine thatthe first user device is actively communicating meshnet data. In thiscase, the first user device may determine that the upgrade triggeringevent has occurred and that the first user device is to upgrade thecommunications.

In another example, the upgrade triggering event may be a time-basedtriggering event associated with the availability of meshnet data forcommunication within a given interval of time. For instance, the firstuser device may monitor an amount of meshnet data that is available forcommunication within the given interval of time (e.g., 60 seconds, 90seconds, 120 seconds, etc.). When the first user device determines thata threshold amount of meshnet data (e.g., 250 bytes, 500 bytes, 1000bytes, etc.) or a threshold rate of data transmission (e.g., 250 bytesper second, 500 bytes per second, 1000 bytes per second, etc.) is notavailable for transmission within the given interval of time (e.g.,threshold amount of meshnet data is not to be communicated within thegiven interval of time), the first user device may determine that thefirst user device is not to upgrade communications to continue toconserve resources. Alternatively, when the first user device determinesthat the threshold amount of meshnet data is available for transmissionwithin the given interval of time (e.g., threshold amount of meshnetdata is to be communicated within the given interval of time), the firstuser device may determine that the first user device is to upgrade thecommunications. In this case, the first user device may determine thatthe upgrade triggering event has occurred.

Based at least in part on determining that the upgrade triggering eventhas occurred, the first user device may transmit an upgrade message tothe second user device. In some aspects, the upgrade message mayindicate to the second user device that meshnet data communicationbetween the first user device and the second user device is to beupgraded such that the meshnet data is to be communicated via themeshnet connection. In some aspects, the upgrade message may include ameshnet data packet with an empty (e.g., blank) payload. In someaspects, the upgrade message may include a meshnet data packet with apayload including a threshold amount of data that satisfies the upgradedata threshold. In this case, subsequent meshnet data may be transmittedvia the meshnet connection. Receiving the upgrade message during meshnetdata communication via the relay connection may indicate to the seconduser device that the meshnet data communication between the first userdevice and the second user device is to be upgraded. As a result, thefirst user device and the second user device may upgrade thecommunications such that meshnet data between the first user device andthe second user device is communicated via the meshnet connection.

In some aspects, the upgrade message may be transmitted to the seconduser device via the relay server, as discussed elsewhere herein. Forinstance, the first user device may encrypt the upgrade messageutilizing the second public key associated with the second user deviceand/or the symmetric key negotiated between the first user device andthe second user device. The first user device may transmit the encryptedupgrade message along with the second public key to the relay server toenable the relay server to relay (e.g., transmit) the encrypted upgrademessage to the second user device. In this case, the first user deviceand/or the second user device may perform one or more processesassociated with block 335 through block 350 to set up a new meshnetconnection. In some aspects, the first user device and/or the seconduser device may renegotiate parameters (e.g., symmetric key, protocol,etc.) to be used for communication over the new meshnet connection.Based at least in part on upgrading the communication, the first userdevice may utilize the new meshnet connection to communicate (e.g.,transmit and/or receive) meshnet data and may again monitor anoccurrence of a downgrade triggering event. In some aspects, the firstuser device and the second user device may continue to utilize the relayconnection to communicate control data and/or a nominal amount of data(e.g., an amount of data that fails to satisfy the data threshold). Inother words, the first user device and/or the second user device maymaintain the relay connection.

In some aspects, the other user devices (e.g., second user device, thirduser device, fourth user device, etc.) included in the mesh network mayoperate to perform conservation of resources in a similar and/oranalogous manner as discussed herein with respect to the first userdevice and/or the second user device. For instance, the other userdevices in the mesh network may, among other things, monitor anoccurrence of a downgrade triggering event, transmit a downgrade messagebased at least in part on determining occurrence of the downgradetriggering event, coordinate to downgrade the communications, monitor anoccurrence of an upgrade triggering event, transmit an upgrade messagebased at least in part on determining occurrence of the upgradetriggering event, coordinate to upgrade the communications, as discussedherein. Additional user devices that enter the mesh network may alsoperform conservation of resources, as discussed herein.

In this way, the user devices may adjust operation such that one userdevice operates as the initiating device and the other user deviceoperates as the responding device. In this way, the user devices mayproceed to communicate to establish the meshnet connection in thepresence of a conflict. Further, instances of inefficient transmissionsand retransmissions of communications among the user devices may bemitigated. As a result, the MSP control infrastructure and therespective client applications may enable efficient utilization of userdevice resources (e.g., processing resources, memory resources, powerconsumption resources, battery life, or the like) and network resources(computational resources, network bandwidth, management resources,processing resources, memory resources, or the like) for performingsuitable tasks associated with the mesh network.

As indicated above, FIG. 3 is provided as an example. Other examples maydiffer from what is described with regard to FIG. 3 .

FIG. 4 is an illustration of an example process 400 associated withconservation of resources in a mesh network, according to variousaspects of the present disclosure. In some aspects, the process 400 maybe performed by a memory and/or a processor/controller (e.g., processingunit 116, processor 720) associated with a user device/endpoint (e.g.,user device 102) running a client application. As shown by referencenumeral 410, process 400 may include determining, by a first device incommunication with a second device via a meshnet connection in a meshnetwork, occurrence of a downgrade triggering event indicating thatcommunication between the first user device and the second user deviceis to be downgraded. For instance, a first device may utilize theassociated memory and/or processor to determine, while in communicationwith a second device via a meshnet connection in a mesh network,occurrence of a downgrade triggering event indicating that communicationbetween the first user device and the second user device is to bedowngraded, as discussed elsewhere herein.

As shown by reference numeral 420, process 400 may include transmitting,by the first device to the second device based at least in part ondetermining occurrence of the downgrade triggering event, a downgrademessage indicating that communication between the first user device andthe second user device is to be downgraded. For instance, the firstdevice may utilize a communication interface (e.g., communicationinterface 770) along with the associated memory and/or processor totransmit, to the second device based at least in part on determiningoccurrence of the downgrade triggering event, a downgrade messageindicating that communication between the first user device and thesecond user device is to be downgraded, as discussed elsewhere herein.

Process 400 may include additional aspects, such as any single aspect orany combination of aspects described below and/or in connection with oneor more other processes described elsewhere herein.

In a first aspect, in process 400, determining occurrence of thedowngrade triggering event includes determining that an amount of datacommunicated via the meshnet connection fails to satisfy a downgradedata threshold.

In a second aspect, alone or in combination with the first aspect, inprocess 400, determining occurrence of the downgrade triggering eventincludes determining a lack of communication of meshnet data via themeshnet connection within a given interval of time.

In a third aspect, alone or in combination with the first through secondaspects, in process 400, determining occurrence of the downgradetriggering event includes determining a lack of availability of meshnetdata to be communicated via the meshnet connection within a giveninterval of time.

In a fourth aspect, alone or in combination with the first through thirdaspects, in process 400, transmitting the downgrade message includestransmitting a meshnet packet with an empty payload.

In a fifth aspect, alone or in combination with the first through fourthaspects, in process 400, transmitting the downgrade message includestransmitting an encrypted downgrade message via a relay server.

In a sixth aspect, alone or in combination with the first through fifthaspects, in process 400, the communication between the first user deviceand the second user device is to be downgraded such that meshnet data isto be communicated via a relay connection.

Although FIG. 4 shows example blocks of the process, in some aspects,the process may include additional blocks, fewer blocks, differentblocks, or differently arranged blocks than those depicted in FIG. 4 .Additionally, or alternatively, two or more of the blocks of the processmay be performed in parallel.

As indicated above, FIG. 4 is provided as an example. Other examples maydiffer from what is described with regard to FIG. 4 .

FIG. 5 is an illustration of an example process 500 associated withconservation of resources in a mesh network, according to variousaspects of the present disclosure. In some aspects, the process 500 maybe performed by a memory and/or a processor/controller (e.g., processingunit 116, processor 720) associated with a user device/endpoint (e.g.,user device 102) running a client application. As shown by referencenumeral 510, process 500 may include monitoring, by a first devicecommunicating meshnet data via a meshnet connection with a second devicein a mesh network, occurrence of a triggering event indicating that thefirst device and the second device are to communicate the meshnet datavia a relay connection. For instance, the first device may utilize theassociated memory and/or processor to monitor, while communicatingmeshnet data via a meshnet connection with a second device in a meshnetwork, occurrence of a triggering event indicating that the firstdevice and the second device are to communicate the meshnet data via arelay connection, as discussed elsewhere herein.

As shown by reference numeral 520, process 500 may determining, by thefirst device, occurrence of the triggering event based at least in parton a rate of communication of the meshnet data via the meshnetconnection. For instance, the first device may utilize the associatedmemory and/or processor to determine occurrence of the triggering eventbased at least in part on a rate of communication of the meshnet datavia the meshnet connection, as discussed elsewhere herein.

As shown by reference numeral 530, process 500 may include transmitting,by the first device to the second device based at least in part ondetermining the occurrence of the triggering event, a message indicatingthat the first device and the second device are to communicate themeshnet data via a relay connection. For instance, the user device mayutilize an associated communication interface (e.g., communicationinterface 770) with the associated memory and/or processor to transmit,to the second device based at least in part on determining theoccurrence of the triggering event, a message indicating that the firstdevice and the second device are to communicate the meshnet data via arelay connection, as discussed elsewhere herein.

Process 500 may include additional aspects, such as any single aspect orany combination of aspects described below and/or in connection with oneor more other processes described elsewhere herein.

In a first aspect, in process 500, monitoring occurrence of thetriggering event includes measuring an amount of the meshnet datacommunicated via the meshnet connection.

In a second aspect, alone or in combination with the first aspect, inprocess 500, determining occurrence of the triggering event includescomparing an amount of the meshnet data communicated per unit time witha data threshold, and determining occurrence of the triggering eventbased at least in part on a result of the comparison.

In a third aspect, alone or in combination with the first through secondaspects, in process 500, determining occurrence of the triggering eventincludes comparing an amount of the meshnet data communicated within agiven time interval with a data threshold, and determining occurrence ofthe triggering event based at least in part on a result of thecomparison.

In a fourth aspect, alone or in combination with the first through thirdaspects, in process 500, transmitting the message to the second deviceincludes transmitting the message to the second device via a relayserver.

In a fifth aspect, alone or in combination with the first through fourthaspects, in process 500, transmitting the message includes encryptingthe message utilizing a public key associated with the second device orutilizing a symmetric key negotiated by the first device and the seconddevice.

In a sixth aspect, alone or in combination with the first through fifthaspects, process 500 may include disconnecting, by the first device, themeshnet connection between the first device and the second device.

Although FIG. 5 shows example blocks of the process, in some aspects,the process may include additional blocks, fewer blocks, differentblocks, or differently arranged blocks than those depicted in FIG. 5 .Additionally, or alternatively, two or more of the blocks of the processmay be performed in parallel.

As indicated above, FIG. 5 is provided as an example. Other examples maydiffer from what is described with regard to FIG. 5 .

FIG. 6 is an illustration of an example process 600 associated withconservation of resources in a mesh network, according to variousaspects of the present disclosure. In some aspects, the process 600 maybe performed by a memory and/or a processor/controller (e.g., processingunit 110, processor 720) associated with a user device (e.g., userdevice 102). As shown by reference numeral 610, process 600 may includedetermining, by a first device communicating meshnet data via a meshnetconnection with a second device in a mesh network, occurrence of adowngrade triggering event indicating that the first device and thesecond device are to communicate the meshnet data via a relayconnection. For instance, the first device may utilize the associatedmemory and/or processor to determine, while communicating meshnet datavia a meshnet connection with a second device in a mesh network,occurrence of a downgrade triggering event indicating that the firstdevice and the second device are to communicate the meshnet data via arelay connection, as discussed elsewhere herein.

As shown by reference numeral 620, process 600 may include transmitting,by the first device to the second device based at least in part ondetermining the occurrence of the downgrade triggering event, adowngrade message indicating that the first device and the second deviceare to communicate the meshnet data via a relay connection. Forinstance, the first device may utilize an associated communicationinterface (e.g., communication interface 770) with the associated memoryand/or processor to transmit, to the second device based at least inpart on determining the occurrence of the downgrade triggering event, adowngrade message indicating that the first device and the second deviceare to communicate the meshnet data via a relay connection, as discussedelsewhere herein.

As shown by reference numeral 630, process 600 may include determining,by the first device communicating the meshnet data via the relayconnection with the second device in the mesh network, occurrence of anupgrade triggering event indicating that the first device and the seconddevice are to communicate the meshnet data via a new meshnet connection.For instance, the first device may utilize the associated memory and/orprocessor to determine, while communicating the meshnet data via therelay connection with the second device in the mesh network, occurrenceof an upgrade triggering event indicating that the first device and thesecond device are to communicate the meshnet data via a new meshnetconnection, as discussed elsewhere herein.

As shown by reference numeral 640, process 600 may include transmitting,by the first device to the second device based at least in part ondetermining the occurrence of the upgrade triggering event, an upgrademessage indicating that the first device and the second device are tocommunicate the meshnet data via the new meshnet connection. Forinstance, the first device may utilize an associated communicationinterface (e.g., communication interface 770) with the associated memoryand/or processor to transmit, to the second device based at least inpart on determining the occurrence of the upgrade triggering event, anupgrade message indicating that the first device and the second deviceare to communicate the meshnet data via the new meshnet connection, asdiscussed elsewhere herein.

Process 600 may include additional aspects, such as any single aspect orany combination of aspects described below and/or in connection with oneor more other processes described elsewhere herein.

In a first aspect, in process 600, determining occurrence of the upgradetriggering event includes comparing an amount of the meshnet datacommunicated per unit time with a data threshold, and determiningoccurrence of the upgrade triggering event based at least in part on aresult of the comparison.

In a second aspect, alone or in combination with the first aspect, inprocess 600, determining occurrence of the upgrade triggering eventincludes comparing an amount of the meshnet data communicated within agiven time interval with a data threshold, and determining occurrence ofthe upgrade triggering event based at least in part on a result of thecomparison.

In a third aspect, alone or in combination with the first through secondaspects, in process 600, transmitting the upgrade message includestransmitting an amount of meshnet data that satisfies a data threshold.

In a fourth aspect, alone or in combination with the first through thirdaspects, process 600 may include communicating with the second device toestablish the new meshnet connection.

In a fifth aspect, alone or in combination with the first through fourthaspects, process 600 may include communicating with the second device tonegotiate a symmetric key to be utilized during communication via thenew meshnet connection.

In a sixth aspect, alone or in combination with the first through fifthaspects, process 600 may include disconnecting, by the first device, themeshnet connection between the first device and the second device.

Although FIG. 6 shows example blocks of the process, in some aspects,the process may include additional blocks, fewer blocks, differentblocks, or differently arranged blocks than those depicted in FIG. 6 .Additionally, or alternatively, two or more of the blocks of the processmay be performed in parallel.

As indicated above, FIG. 6 is provided as an example. Other examples maydiffer from what is described with regard to FIG. 6 .

FIG. 7 is an illustration of example devices 700 associated withconservation of resources in a mesh network, according to variousaspects of the present disclosure. In some aspects, the example devices700 may form part of or implement the systems, servers, environments,infrastructures, components, devices, or the like described elsewhereherein (e.g., MSP control infrastructure, VPN server, etc.) and may beused to perform example processes described elsewhere herein. Theexample devices 700 may include a universal bus 710 communicativelycoupling a processor 720, a memory 730, a storage component 740, aninput component 750, an output component 760, and a communicationinterface 770.

Bus 710 may include a component that permits communication amongmultiple components of a device 700. Processor 720 may be implemented inhardware, firmware, and/or a combination of hardware and software.Processor 720 may take the form of a central processing unit (CPU), agraphics processing unit (GPU), an accelerated processing unit (APU), amicroprocessor, a microcontroller, a digital signal processor (DSP), afield-programmable gate array (FPGA), an application-specific integratedcircuit (ASIC), or another type of processing component. In someaspects, processor 720 may include one or more processors capable ofbeing programmed to perform a function. Memory 730 may include a randomaccess memory (RAM), a read only memory (ROM), and/or another type ofdynamic or static storage device (e.g., a flash memory, a magneticmemory, and/or an optical memory) that stores information and/orinstructions for use by processor 720.

Storage component 740 may store information and/or software related tothe operation and use of a device 700. For example, storage component740 may include a hard disk (e.g., a magnetic disk, an optical disk,and/or a magneto-optic disk), a solid state drive (SSD), a compact disc(CD), a digital versatile disc (DVD), a floppy disk, a cartridge, amagnetic tape, and/or another type of non-transitory computer-readablemedium, along with a corresponding drive.

Input component 750 may include a component that permits a device 700 toreceive information, such as via user input (e.g., a touch screendisplay, a keyboard, a keypad, a mouse, a button, a switch, and/or amicrophone). Additionally, or alternatively, input component 750 mayinclude a component for determining location (e.g., a global positioningsystem (GPS) component) and/or a sensor (e.g., an accelerometer, agyroscope, an actuator, another type of positional or environmentalsensor, and/or the like). Output component 760 may include a componentthat provides output information from device 700 (via, for example, adisplay, a speaker, a haptic feedback component, an audio or visualindicator, and/or the like).

Communication interface 770 may include a transceiver-like component(e.g., a transceiver, a separate receiver, a separate transmitter,and/or the like) that enables a device 700 to communicate with otherdevices, such as via a wired connection, a wireless connection, or acombination of wired and wireless connections. Communication interface770 may permit device 700 to receive information from another deviceand/or provide information to another device. For example, communicationinterface 770 may include an Ethernet interface, an optical interface, acoaxial interface, an infrared interface, a radio frequency (RF)interface, a universal serial bus (USB) interface, a Wi-Fi interface, acellular network interface, and/or the like.

A device 700 may perform one or more processes described elsewhereherein. A device 700 may perform these processes based on processor 720executing software instructions stored by a non-transitorycomputer-readable medium, such as memory 730 and/or storage component740. As used herein, the term “computer-readable medium” may refer to anon-transitory memory device. A memory device may include memory spacewithin a single physical storage device or memory space spread acrossmultiple physical storage devices.

Software instructions may be read into memory 730 and/or storagecomponent 740 from another computer-readable medium or from anotherdevice via communication interface 770. When executed, softwareinstructions stored in memory 730 and/or storage component 740 may causeprocessor 720 to perform one or more processes described elsewhereherein. Additionally, or alternatively, hardware circuitry may be usedin place of or in combination with software instructions to perform oneor more processes described elsewhere herein. Thus, implementationsdescribed herein are not limited to any specific combination of hardwarecircuitry and software.

The quantity and arrangement of components shown in FIG. 7 are providedas an example. In practice, a device 700 may include additionalcomponents, fewer components, different components, or differentlyarranged components than those shown in FIG. 7 . Additionally, oralternatively, a set of components (e.g., one or more components) of adevice 700 may perform one or more functions described as beingperformed by another set of components of a device 700.

As indicated above, FIG. 7 is provided as an example. Other examples maydiffer from what is described with regard to FIG. 7 .

Persons of ordinary skill in the art will appreciate that the aspectsencompassed by the present disclosure are not limited to the particularexemplary aspects described herein. In that regard, althoughillustrative aspects have been shown and described, a wide range ofmodification, change, and substitution is contemplated in the foregoingdisclosure. It is understood that such variations may be made to theaspects without departing from the scope of the present disclosure.Accordingly, it is appropriate that the appended claims be construedbroadly and in a manner consistent with the present disclosure.

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the aspects to the preciseform disclosed. Modifications and variations may be made in light of theabove disclosure or may be acquired from practice of the aspects.

As used herein, the term “component” or “device” is intended to bebroadly construed as hardware, firmware, or a combination of hardwareand software. As used herein, a processor is implemented in hardware,firmware, or a combination of hardware and software.

As used herein, satisfying a threshold may, depending on the context,refer to a value being greater than the threshold, greater than or equalto the threshold, less than the threshold, less than or equal to thethreshold, equal to the threshold, or not equal to the threshold, amongother examples, or combinations thereof.

It will be apparent that systems or methods described herein may beimplemented in different forms of hardware, firmware, or a combinationof hardware and software. The actual specialized control hardware orsoftware code used to implement these systems or methods is not limitingof the aspects. Thus, the operation and behavior of the systems ormethods were described herein without reference to specific softwarecode—it being understood that software and hardware can be designed toimplement the systems or methods based, at least in part, on thedescription herein.

Even though particular combinations of features are recited in theclaims or disclosed in the specification, these combinations are notintended to limit the disclosure of various aspects. In fact, many ofthese features may be combined in ways not specifically recited in theclaims or disclosed in the specification. Although each dependent claimlisted below may directly depend on only one claim, the disclosure ofvarious aspects includes each dependent claim in combination with everyother claim in the claim set. A phrase referring to “at least one of” alist of items refers to any combination of those items, including singlemembers. As an example, “at least one of: a, b, or c” is intended tocover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination withmultiples of the same element (for example, a-a, a-a-a, a-a-b, a-a-c,a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c or any other ordering ofa, b, and c).

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and may be used interchangeably with “one or more.” Further, asused herein, the article “the” is intended to include one or more itemsreferenced in connection with the article “the” and may be usedinterchangeably with “the one or more.” Furthermore, as used herein, theterm “set” is intended to include one or more items (e.g., relateditems, unrelated items, a combination of related and unrelated items,etc.), and may be used interchangeably with “one or more.” Where onlyone item is intended, the phrase “only one” or similar language is used.Also, as used herein, the terms “has,” “have,” “having,” or the like areintended to be open-ended terms. Further, the phrase “based on” isintended to mean “based, at least in part, on” unless explicitly statedotherwise. Also, as used herein, the term “or” is intended to beinclusive when used in a series and may be used interchangeably with“and/or,” unless explicitly stated otherwise (e.g., if used incombination with “either” or “only one of”).

What is claimed is:
 1. A method, comprising: determining, by a firstdevice communicating meshnet data via a meshnet connection with a seconddevice in a mesh network, occurrence of a downgrade triggering eventindicating that the first device and the second device are tocommunicate the meshnet data via a relay connection; transmitting, bythe first device to the second device based at least in part ondetermining the occurrence of the downgrade triggering event, adowngrade message indicating that the first device and the second deviceare to communicate the meshnet data via the relay connection;determining, by the first device communicating the meshnet data via therelay connection with the second device in the mesh network, occurrenceof an upgrade triggering event indicating that the first device and thesecond device are to communicate the meshnet data via a new meshnetconnection; and transmitting, by the first device to the second devicebased at least in part on determining the occurrence of the upgradetriggering event, an upgrade message indicating that the first deviceand the second device are to communicate the meshnet data via the newmeshnet connection, wherein determining occurrence of the upgradetriggering event includes comparing an amount of the meshnet datacommunicated within a given time interval with a data threshold, anddetermining occurrence of the upgrade triggering event based at least inpart on a result of the comparison.
 2. The method of claim 1, whereindetermining occurrence of the upgrade triggering event includescomparing an amount of the meshnet data communicated per unit time witha data threshold, and determining occurrence of the upgrade triggeringevent based at least in part on a result of the comparison.
 3. Themethod of claim 1, wherein determining occurrence of the upgradetriggering event includes determining occurrence of the upgradetriggering event when the result of the comparison indicates that theamount of the meshnet data communicated within the given time intervalsatisfies the data threshold.
 4. The method of claim 1, whereintransmitting the upgrade message includes transmitting an amount ofmeshnet data that satisfies a data threshold.
 5. The method of claim 1,further comprising: communicating with the second device to establishthe new meshnet connection.
 6. The method of claim 1, furthercomprising: communicating with the second device to negotiate asymmetric key to be utilized during communication via the new meshnetconnection.
 7. The method of claim 1, further comprising: disconnecting,by the first device, the meshnet connection between the first device andthe second device.
 8. A first device, comprising: a memory; and aprocessor communicatively coupled to the memory, the memory and theprocessor being configured to: determine, while communicating meshnetdata via a meshnet connection with a second device in a mesh network,occurrence of a downgrade triggering event indicating that the firstdevice and the second device are to communicate the meshnet data via arelay connection; transmit, to the second device based at least in parton determining the occurrence of the downgrade triggering event, adowngrade message indicating that the first device and the second deviceare to communicate the meshnet data via the relay connection; determine,while communicating the meshnet data via the relay connection with thesecond device in the mesh network, occurrence of an upgrade triggeringevent indicating that the first device and the second device are tocommunicate the meshnet data via a new meshnet connection; and transmit,to the second device based at least in part on determining theoccurrence of the upgrade triggering event, an upgrade messageindicating that the first device and the second device are tocommunicate the meshnet data via the new meshnet connection, wherein todetermine occurrence of the upgrade triggering event, the memory and theprocessor are configured to compare an amount of the meshnet datacommunicated within a given time interval with a data threshold, and todetermine occurrence of the upgrade triggering event based at least inpart on a result of the comparison.
 9. The first device of claim 8,wherein, to determine occurrence of the upgrade triggering event, thememory and the processor are configured to compare an amount of themeshnet data communicated per unit time with a data threshold, and todetermine occurrence of the upgrade triggering event based at least inpart on a result of the comparison.
 10. The first device of claim 8,wherein, to determine occurrence of the upgrade triggering event, thememory and the processor are configured to determine occurrence of theupgrade triggering event when the result of the comparison indicatesthat the amount of the meshnet data communicated within the given timeinterval satisfies the data threshold.
 11. The first device of claim 8,wherein, to transmit the upgrade message, the memory and the processorare configured to transmit an amount of meshnet data that satisfies adata threshold.
 12. The first device of claim 8, wherein the memory andthe processor are configured to: communicate with the second device toestablish the new meshnet connection.
 13. The first device of claim 8,wherein the memory and the processor are configured to: communicate withthe second device to negotiate a symmetric key to be utilized duringcommunication via the new meshnet connection.
 14. The first device ofclaim 8, wherein the memory and the processor are configured to:disconnect the meshnet connection between the first device and thesecond device.
 15. A non-transitory computer-readable medium configuredto store instructions, which when executed by a processor associatedwith a first device, cause the processor to: determine, whilecommunicating meshnet data via a meshnet connection with a second devicein a mesh network, occurrence of a downgrade triggering event indicatingthat the first device and the second device are to communicate themeshnet data via a relay connection; transmit, to the second devicebased at least in part on determining the occurrence of the downgradetriggering event, a downgrade message indicating that the first deviceand the second device are to communicate the meshnet data via the relayconnection; determine, while communicating the meshnet data via therelay connection with the second device in the mesh network, occurrenceof an upgrade triggering event indicating that the first device and thesecond device are to communicate the meshnet data via a new meshnetconnection; and transmit, to the second device based at least in part ondetermining the occurrence of the upgrade triggering event, an upgrademessage indicating that the first device and the second device are tocommunicate the meshnet data via the new meshnet connection, wherein todetermine occurrence of the upgrade triggering event, the processor isconfigured to compare an amount of the meshnet data communicated withina given time interval with a data threshold, and to determine occurrenceof the upgrade triggering event based at least in part on a result ofthe comparison.
 16. The non-transitory computer-readable medium of claim15, wherein, to determine occurrence of the upgrade triggering event,the processor is configured to compare an amount of the meshnet datacommunicated per unit time with a data threshold, and to determineoccurrence of the upgrade triggering event based at least in part on aresult of the comparison.
 17. The non-transitory computer-readablemedium of claim 15, wherein, to determine occurrence of the upgradetriggering event, the processor is configured to determine occurrence ofthe upgrade triggering event when the result of the comparison indicatesthat the amount of the meshnet data communicated within the given timeinterval satisfies the data threshold.
 18. The non-transitorycomputer-readable medium of claim 15, wherein, to transmit the upgrademessage, the processor is configured to transmit an amount of meshnetdata that satisfies a data threshold.
 19. The non-transitorycomputer-readable medium of claim 15, wherein the processor isconfigured to: communicate with the second device to establish the newmeshnet connection.
 20. The non-transitory computer-readable medium ofclaim 15, wherein the processor is configured to: communicate with thesecond device to negotiate a symmetric key to be utilized duringcommunication via the new meshnet connection.